Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Summer cleaning #216

Merged
merged 8 commits into from
Aug 21, 2017
Merged

Summer cleaning #216

merged 8 commits into from
Aug 21, 2017

Conversation

daviddias
Copy link
Member

@daviddias
Copy link
Member Author

image

Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙇‍♂️

README.md Outdated

[libp2p](https://github.com/libp2p/specs) is a networking stack and library modularized out of [The IPFS Project](https://github.com/ipfs/ipfs), and bundled separately for other tools to use.
>
libp2p is the product of a long, and arduous quest of understanding -- a deep dive into the internet's network stack, and plentiful peer-to-peer protocols from the past. Building large scale peer-to-peer systems has been complex and difficult in the last 15 years, and libp2p is a way to fix that. It is a "network stack" -- a protocol suite -- that cleanly separates concerns, and enables sophisticated applications to only use the protocols they absolutely need, without giving up interoperability and upgradeability. libp2p grew out of IPFS, but it is built so that lots of people can use it, for lots of different projects.
>
> We will be writing a set of docs, posts, tutorials, and talks to explain what p2p is, why it is tremendously useful, and how it can help your existing and new projects. But in the meantime, check out
>
> - [**The IPFS Network Spec**](https://github.com/libp2p/specs), which grew into libp2p
> - [**The libp2p Specification**](https://github.com/libp2p/specs), which grew into libp2p
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd remove the "which grew into libp2p" part (only makes sense when we call it the "IPFS Network Spec").

README.md Outdated

# Usage
There is currently only one bundle of `go-libp2p`, this package. This bundle is used by [`go-ipfs`](https://github.com/ipfs/go-ipfs).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this statement really serve any purpose?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We mention bundles on the website and the JavaScript version. I know that right now everything gets a bit hardcoded in go-libp2p, but ideally we would be able to create multiple bundles with different features easily (think different runtimes)

README.md Outdated
# Usage
There is currently only one bundle of `go-libp2p`, this package. This bundle is used by [`go-ipfs`](https://github.com/ipfs/go-ipfs).

## Usage

`go-libp2p` repo will be a place holder for the list of Go modules that compose Go libp2p, as well as its entry point.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/will be/is

README.md Outdated

### Dependencies

While developing, you need to use gx to install and link your dependencies, to do that, run:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have some explanation of gx we can link to. If you don't know what gx is, this instruction will be very confusing.

README.md Outdated

### Tests

Running of individual tests is done through `go test <path to test>`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're going to give people gx instructions, we might as well tell them to run gx test ...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd tell users to call gx test here as well.

README.md Outdated
- [**Website**](https://github.com/libp2p/website)
| Package | Version | CI |
|--------------------|---------|---------------------|
| **Transports** |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume this section is WIP.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is indeed

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a "(WIP)" marker here. Otherwise, this is a bit confusing.

README.md Outdated

- read the [libp2p spec](https://github.com/libp2p/specs)
- please make branches + pull-request, even if working on the main repository
- ask questions or talk about things in [Issues](https://github.com/ipfs/go-ipfs/issues) or #ipfs on freenode.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should update this (and any other documents that tell users to do this).

TODO Outdated
@@ -1 +1 @@
- pull mdns out as its own separate package
- [ ] pull mdns out as its own separate package
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd just remove this file and file an issue.

@@ -46,7 +43,7 @@ libp2p-peer addresses:
The run the local peer, indicating that it will need to forward http requests to the remote peer as follows:

```
$ ./http-proxy -d /ip4/127.0.0.1/tcp/12000/ipfs/QmddTrQXhA9AkCpXPTkcY7e22NK73TwkUms3a44DhTKJTD
> ./http-proxy -d /ip4/127.0.0.1/tcp/12000/ipfs/QmddTrQXhA9AkCpXPTkcY7e22NK73TwkUms3a44DhTKJTD
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any particular reason for this change? Historically, $ has meant "prompt where user is not root" and # has meant "prompt where user is root".

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There was a conversation a long time ago between Juan and Richard where they questioned what was the most valid character to represent the prompt and the result of the conversation was >.

As for #, we use it everywhere as comments since it is the character for line comments in bash.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(:roll_eyes:) Unfortunately, that argument kind of makes sense. $ for variables, # for comments, > for prompts.


But really,

𝝺: echo "there can be only one"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ahaha :)

can this get merged then?

@daviddias
Copy link
Member Author

Thanks for the review @Stebalien :)

@daviddias
Copy link
Member Author

Can this be merged? :)

Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(with nits)

README.md Outdated

### Tests

Running of individual tests is done through `go test <path to test>`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd tell users to call gx test here as well.

README.md Outdated
- [**Website**](https://github.com/libp2p/website)
| Package | Version | CI |
|--------------------|---------|---------------------|
| **Transports** |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a "(WIP)" marker here. Otherwise, this is a bit confusing.

README.md Outdated
| **Crypto Channels** |
| **Peer Routing** |
| **Content Routing** |
| **Generics** |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean by "generics". To me, "generics" usually means something like Java generics but go doesn't have those...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fair point, specially with all the discussion about generics in go land. Renamed to Miscellaneous, it is the packages that don't fit a specific category.

@Stebalien Stebalien merged commit c50d6f5 into master Aug 21, 2017
@daviddias daviddias removed the status/in-progress In progress label Aug 21, 2017
@Stebalien
Copy link
Member

💖

@daviddias daviddias deleted the feat/summer-cleaning branch August 21, 2017 20:14
marten-seemann added a commit that referenced this pull request Apr 22, 2022
close all UDP connections when the reuse is closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants